home *** CD-ROM | disk | FTP | other *** search
- Path: howland.reston.ans.net!psinntp!psinntp!psinntp!psinntp!usenet
- From: grantp@usa.pipeline.com(Pete Grant)
- Newsgroups: comp.lang.c++
- Subject: Re: Disappearing Wait Cursor
- Date: 17 Apr 1996 10:50:39 GMT
- Organization: Kalevi, Inc.
- Message-ID: <4l2idv$d8o@news1.h1.usa.pipeline.com>
- References: <31744308.6222@dbcorp.ab.ca>
- NNTP-Posting-Host: 38.8.120.10
- X-PipeUser: grantp
- X-PipeHub: usa.pipeline.com
- X-PipeGCOS: (Pete Grant)
- X-Newsreader: Pipeline v3.5.0
-
- On Apr 16, 1996 19:02:00 in article <Disappearing Wait Cursor>, 'Charlotte
- Moller <cmoller@dbcorp.ab.ca>' wrote:
-
-
- >Disappearing wait cursor (hour-glass)
- >-------------------------------------
- >
- >Has anyone ever come across this problem when developing Windows
- >programs which access Oracle databases?
- >
- >When I have to perform an activity that I know is going to take a little
- >while, I've being setting the wait cursor (hourglass) via the windows
- >call hcursor = SetCursor(LoadCursor(NULL, IDC_WAIT)), and then restoring
- >the cursor after the activity via SetCursor(hcursor). This appears to
- >work fine, except when I am accessing the Orracle database via SQL*Net.
- >Somewhere during the activity the wait cursor disappears! This happens
- >with any time consuming database access. With a click happy user, the
- >results are disastrous, usually ending in a GPF. I'm currently
- >programming in Borland C++ 3.1 / OWL 1.0 using the CommonBase library
- >(by ImageSoft) for database access, but I've seen this problem with
- >other development environments (i.e. ObjectView, calls from a C++
- >program to R&R ReportWriter). My best guess is SQL*Net does something
- >nasty with the cursor, but a solution has thus far eluded me.
- >
- >Thanks :),
- >Charlotte
- Are you using SetCapture()/ReleaseCapture() in addition to
- setting the cursor? If not, you should experience the
- phenomena at other times also.
-
- If you do not SetCapture(), the cursor is changed to that of
- the window over which the mouse pointer is currently positioned.
- Additionally, if the user moves the mouse away from your 'base'
- window and then back, the cursor is returned to its default shape;
- i.e., the one specified in the WNDCLASS structure.
-
- Now, if you SetCapture(), and SQLNet does also, you're out
- of luck.
- --
- Pete Grant
- Kalevi, Inc.
- Software Engineering & development
-